Get help with
Roomie Remote X.

Google requires end users to set up their own Device Access project to enable Nest thermostat control. While there are many steps involved, once completed, it works quite well. Read all steps before starting.

Prerequisites

• A working Google Account with at least one Nest thermostat associated and controllable via the Google Home or Nest app.
• Use a real browser on a computer (Google Chrome recommended). Do not use a mobile device for these steps.
• Have an empty note ready — you will need to save a Project ID, Client ID, and iOS URL Scheme (each roughly 80-character strings unique to you).

Step 1: Register for Device Access

• Go to developers.google.com/nest/device-access and click Go to console.
• There is a one-time non-refundable $5 registration fee paid to Google.

Step 2: Create a Project

• On the Device Access Console, tap Create project.
• Enter a unique project name such as "Roomie – Smith Family".
• When asked to "Add your OAuth client ID", click Skip for now.
• On the Events screen, select Disable, then click Create Project.
• The next screen shows your project with a Project ID. Copy this to your note.

Step 3: Enable the API and Create OAuth Credentials

• Go to developers.google.com/nest/device-access/get-started and click Enable the API and get an OAuth 2.0 Client ID.
• On the "Enable Smart Device Management API" popup, enter a project title (e.g. "Roomie – SDM – Smith Family"), agree to the license terms, and click Next.
• For "Specify the product name", enter something like "Roomie – Smith Family".
• For application type, select iOS.
• For Bundle ID, enter com.roomie.unified exactly.
• You can ignore the download/copy prompts for now.

Step 4: Enable the Smart Device Management API

• Go to console.developers.google.com/apis/library/smartdevicemanagement.googleapis.com and click Enable if needed.

Step 5: Create Credentials

• Go to console.developers.google.com/apis/credentials and make sure the Smart Device Management API is selected.
• Tap the Credentials tab, then +CREATE CREDENTIALS.
• Under "What data will you be accessing?" select User Data.
• Under App Information, enter Roomie Remote for the app name and your email for "User support email". Skip the logo upload.
• Under Scopes, tap "Add or Remove Scopes" and select all scopes in rows labeled Smart Device Management API (there are at least 9). Save and Continue.
• On the "OAuth Client ID" screen, select iOS as the Application Type.
• Enter com.roomie.unified as the Bundle ID, 1455871956 as the App Store ID, and DDDDD99DD9 as the Team ID. Tap CREATE.
• On the "Download your credentials" screen, copy the Client ID to your note. Click Done.

Step 6: Copy the iOS URL Scheme

• Back on the Smart Device Management API screen, tap the Credentials tab, then tap iOS Client 1.
• Copy both the Client ID and iOS URL Scheme to your note.

Step 7: Link OAuth Client to Your Project

• Return to the Device Access Console at console.nest.google.com/device-access and tap your project.
• Next to "OAuth client ID", open the 3-dot menu and select Add Client ID.
• Paste your Client ID (it looks like "101010101-abababababab.apps.googleusercontent.com"). Save it.

Step 8: Configure the OAuth Consent Screen

• Go to console.cloud.google.com/apis/credentials/consent.
• Ensure the consent screen is configured for External users.
• Under Test users, add your Google Account email address — the same account associated with your Nest thermostats.

Step 9: Add the Cloud Service in Roomie

• You should now have a Project ID, Client ID, and iOS URL Scheme in your note.
• In Roomie, add the Google Nest Cloud Service from the Devices panel.
• Enter the Project ID, Client ID, and Scheme into the fields shown.
• When complete, the Pair button will appear. Proceed with pairing.
• Make sure to allow access and turn on each thermostat in the Google authentication and permissions panels that appear.
• Pairing is complete. The thermostats will appear in the Thermostats section of the Homebar.

Roomie Remote includes a Local Network Control HTTP API on port 47147 for starting activities and sending device commands from any system on your local network. This enables integration with home automation controllers, custom scripts, and third-party systems.

All API endpoints use JSON. Responses follow this format:

{
  "st" : "success" | "fail" | "error",
  "da" : <response data>,
  "co" : <HTTP status code>
}

A "st" value of "success" means the request was handled. "fail" indicates a problem with the request data. "error" indicates a server-side problem.

List Activities

Returns all activities in the active Roomie configuration with their UUIDs.

Response data: array of activity objects:

{
  "icon" :     <string: Activity icon name>,
  "roomuuid" : <string: UUID of the room>,
  "name" :     <string: Activity name>,
  "toggle" :   <boolean: Toggle state after starting>,
  "type" :     <string: "off" if PowerOff activity>,
  "uuid" :     <string: Activity UUID>
}

Note: Toggle activities are listed twice. The "on" UUID has a + suffix and the "off" UUID has a - suffix. The name contains "(On)" or "(Off)".

10.3 Beta Each activity object now also exposes the device UUIDs bound to its volume, transport (source), guide, and aux roles. Each field is present only when the activity defines that binding — test for key presence rather than nil/empty. These let external bridges route their own commands (e.g. "send VolumeUp to whichever device owns volume in the active activity") without going through the higher-level /api/v1/remote/press endpoint below.

{
  "vuuid" :     <optional string: Volume device UUID>,
  "openuuid" :  <optional string: Transport / source device UUID>,
  "guideuuid" : <optional string: Guide device UUID>,
  "auxuuids" :  <optional array: Aux device UUIDs>
}

$ curl -X GET 'http://<roomie-ip>:47147/api/v1/activities'

{
  "st" : "success",
  "da" : [
    {
      "icon" : "logo-tivo",
      "roomuuid" : "D3579B0E-6E36-...",
      "name" : "Living Room: Watch TiVo",
      "uuid" : "4A4A6B37-BE64-...",
      "vuuid" : "AB12CD34-...",
      "openuuid" : "EF56AB78-..."
    },
    {
      "icon" : "curtains",
      "roomuuid" : "D3579B0E-6E36-...",
      "name" : "Living Room: Shades (On)",
      "toggle" : true,
      "uuid" : "2FC827F4-FF07-...+"
    }
  ],
  "co" : 200
}

Run Activity

Execute a specific activity. Supports optional delay and toggle state control.

{
  "au" : <required string: Activity UUID>,
  "ts" : <optional string: "on" | "off" — toggle state>,
  "de" : <optional integer: delay in seconds, must be > 1.0>
}

A simplified GET variation is available for systems that don't support JSON:

Note: Advanced options like delay are not available with the simplified GET syntax.

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/runactivity' \
  -d '{ "au" : "53B7B23B-F70F-498D-A128-477FCBD05A58" }'

{ "st" : "success", "da" : {}, "co" : 200 }

List Devices

Returns all devices in the active configuration with UUIDs and properties.

Response data: array of device objects:

{
  "address" :  <string: Device IP address>,
  "port" :     <integer: Device port>,
  "model" :    <string: Device model>,
  "uuid" :     <string: Device UUID>,
  "roomname" : <string: Room name>,
  "brand" :    <string: Device brand>,
  "type" :     <string: Device type>,
  "name" :     <string: Device name>,
  "roomuuid" : <string: Room UUID>
}

$ curl -X GET 'http://<roomie-ip>:47147/api/v1/devices'

{
  "st" : "success",
  "da" : [
    {
      "address" : "10.0.0.49",
      "port" : 8060,
      "model" : "All Models",
      "uuid" : "A94CF6C9-D458-...",
      "roomname" : "Living Room",
      "brand" : "Roku",
      "type" : "Player",
      "name" : "Roku Media Player",
      "roomuuid" : "D3579B0E-6E36-..."
    }
  ],
  "co" : 200
}

Send Device Command

Send a command to a specific device. If a repeat option is specified, use the refresh API to keep the command repeating — sessions expire after 0.3 seconds.

{
  "de" : <optional string: Delay in ms before sending>,
  "cs" : [
    {
      "ty" : <required: "command" | "activity" | "url">,
      "de" : <optional string: Delay in ms>,
      "pa" : { ... }  // Params vary by type
    }
  ]
}

Command params ("ty": "command"):

{
  "cm" :     <required: Command name in caps>,
  "device" : <required: Device UUID>,
  "cd" :     <optional: { "au": toggle UUID, "ts": "on"|"off" }>,
  "pd" :     <optional: Power delay in ms>,
  "dl" :     <optional: "yes"|"no" delay devices globally>,
  "re" :     <optional: "constant"|"progressive" repeat type>,
  "pa" :     <optional: Array of up to 3 parameter strings>
}

Activity params ("ty": "activity"):

{
  "au" : <required: Activity UUID>,
  "ts" : <optional: "on"|"off" toggle state>
}

URL params ("ty": "url"):

{
  "ur" : <required: URL to load, include scheme (http://)>
}

Note: The API currently handles a single command despite accepting an array. The response includes a session identifier for managing repeating commands.

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/sendcommands' \
  -d '{ "de": "1000", "cs": [ { "ty": "command",
    "pa": { "cm": "VOLUME UP",
    "device": "2DCCA135-4264-...",
    "re": "constant" } } ] }'

{
  "st" : "success",
  "da" : { "se" : "96F4C281-B34D-..." },
  "co" : 200
}

Refresh Command Session

Keep a repeating command alive. Sessions expire after 0.3 seconds — call this more frequently to continue repeating. Not needed if sendcommands was called without a repeat option.

{
  "se" : <required: Command session identifier>
}

Stop Command Session

Stop a repeating command immediately rather than waiting for the 0.3-second session timeout. Not needed if sendcommands was called without a repeat option.

{
  "se" : <required: Command session identifier>
}

Broadcast Audio File

Play an audio file (wav, aif, or mp3) on all Roomie instances currently open and in the foreground, including Apple TV. Files must first be added via Roomie's Settings > Add Custom Media.

$ curl -X GET 'http://<roomie-ip>:47147/api/v1/media/doorbell.wav'

List Rooms 10.3 Beta

Returns each room with its currently-running activity (if any) and an ordered list of visible activities. Bridges call this once during pairing to let the user choose which room a hard-button remote controls.

Response data: array of room objects.

{
  "roomuuid" :            <string: Room UUID>,
  "roomname" :            <string: Room name>,
  "currentactivityuuid" : <optional string: Active activity UUID>,
  "currentactivityname" : <optional string: Active activity name>,
  "activities" : [
    { "activityuuid" : <string>, "name" : <string> }
  ]
}

Note: The activities array is filtered to visible non-off activities only — the same set that Activity1 through Activity8 indexes into in /api/v1/remote/press.

$ curl -X GET 'http://<roomie-ip>:47147/api/v1/rooms'

{
  "st" : "success",
  "da" : [
    {
      "roomuuid" : "D3579B0E-6E36-...",
      "roomname" : "Living Room",
      "currentactivityuuid" : "4A4A6B37-BE64-...",
      "currentactivityname" : "Watch Apple TV",
      "activities" : [
        { "activityuuid" : "4A4A6B37-BE64-...", "name" : "Watch Apple TV" },
        { "activityuuid" : "B12CD34E-5F67-...", "name" : "Watch Cable" }
      ]
    }
  ],
  "co" : 200
}

Universal Remote — Press 10.3 Beta

Dispatches a symbolic button press. Roomie resolves the button against the addressed room's currently-running activity and sends the appropriate device command — no need for the caller to know which device owns each function.

{
  "button" :       <required string: Lexicon name (see below)>,
  "roomuuid" :     <preferred string: Target room UUID>,
  "roomname" :     <optional string: Target room name (case-insensitive)>,
  "activityuuid" : <optional string: Override the currently-running activity>,
  "action" :       <optional string: "tap" | "press" | "release" | "repeat">,
  "digits" :       <optional string: Channel number (Channel button only)>,
  "count" :        <optional integer: Number of taps (action=repeat only)>,
  "hold_ms" :      <optional integer: Auto-release delay in ms (action=press only)>,
  "session" :      <required string for action=release: Session UUID to end>
}

Addressing resolution order:

1. activityuuid override — searched across all rooms.
2. roomuuid — current activity for that room.
3. roomname (case-insensitive) — current activity for the matched room.
4. Last-used room fallback — ambiguous on multi-room installs; provided for single-room or dev/test only.

Action semantics:

• tap (default) — single dispatch.
• press — start a continuously-repeating command; returns a session to end with release (or use hold_ms for server-side auto-release).
• release — end the named session. Equivalent to /api/v1/stopcommands with the session.
• repeat — fire count discrete taps with a small inter-tap delay.

Status codes:

• 200 — dispatched successfully.
• 400 — missing or unknown button; missing session for release.
• 404 — unknown room or activity; ActivityN beyond the room's visible activity count.
• 409 — room found but no activity currently running.
• 422 — activity has no binding for the button's role (e.g. Pause in a Hue-only scene).

Button lexicon (send any name verbatim):

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/remote/press' \
  -d '{ "button": "VolumeUp", "roomuuid": "D3579B0E-...", "action": "press" }'

{ "st": "success",
  "da": { "button": "VolumeUp", "role": "volume",
          "deviceuuid": "AB12CD34-...", "command": "VolumeUp",
          "session": "96F4C281-...", "dispatched": true },
  "co": 200 }

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/remote/press' \
  -d '{ "action": "release", "session": "96F4C281-..." }'

{ "st": "success", "da": { "dispatched": true, "session": "96F4C281-..." }, "co": 200 }

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/remote/press' \
  -d '{ "button": "Channel", "roomuuid": "D3579B0E-...", "digits": "704" }'

$ curl -X POST 'http://<roomie-ip>:47147/api/v1/remote/press' \
  -d '{ "button": "Activity2", "roomuuid": "D3579B0E-..." }'

Universal Remote — Capabilities 10.3 Beta

Returns the resolution result for every button in the lexicon, scoped to the addressed activity. Smart bridges use this to dim or hide buttons that wouldn't dispatch successfully — a single round trip instead of probing each button.

Same addressing query parameters as /remote/press: roomuuid, roomname, or activityuuid.

Response data:

{
  "roomuuid" :        <string>,
  "roomname" :        <string>,
  "activityuuid" :    <string>,
  "activityname" :    <string>,
  "lexicon_version" : <integer: Increments when buttons are added>,
  "buttons" : {
    "<ButtonName>" : <resolution dict, or null if unsupported in this activity>,
    ...
  }
}

$ curl -X GET 'http://<roomie-ip>:47147/api/v1/remote/capabilities?roomuuid=D3579B0E-...'

{
  "st" : "success",
  "da" : {
    "roomname" : "Living Room",
    "activityname" : "Watch Apple TV",
    "lexicon_version" : 1,
    "buttons" : {
      "VolumeUp"  : { "deviceuuid": "AB12CD34-...", "role": "volume",    "command": "VolumeUp" },
      "Play"      : { "deviceuuid": "EF56AB78-...", "role": "transport", "command": "Play" },
      "ChannelUp" : null,
      "Activity1" : { "activityuuid": "4A4A6B37-...", "activityname": "Watch Apple TV", "role": "activity" }
    }
  },
  "co" : 200
}

HTTP Activity & Device Command Interface v9.2 — Updated December 2, 2024 · Universal Remote endpoints (10.3 Beta) added April 2026

1. Verify the device's own IP control settings are enabled in its menu system. Enable Network Standby if the option exists. Confirm the device has a valid network address.
2. Use the Test button when adding the device to confirm the correct command set.
3. Some devices (like Samsung TVs) require you to manually approve the control device on the TV screen. Some pre-2016 Samsung TVs don't support IP power-on at all.
4. Check that the device firmware is up to date.
5. If the device was added via Manual IP, verify the IP address hasn't changed. We recommend static IPs or DHCP reservations for all manually-added devices.
6. For devices that require Wake on LAN to power on, make sure the +WAKE ON LAN command is included in your Activity's start sequence.

First, select which IR adapter you're using:

1. Check your router settings — make sure "Enable Multicast" and "Enable UPnP" are turned on.
2. Restart everything — power-cycle your iPhone/iPad/Mac, router(s), and target devices. This clears a surprising number of multicast issues.
3. If using a mesh Wi-Fi system (Eero, UniFi, Google Wifi, etc.), ensure multicast/mDNS forwarding is enabled across all access points — some mesh systems isolate multicast by default.
4. For older receivers, unplug them completely for 30 seconds, plug back in, and wait 60 seconds before re-attempting discovery.
5. If discovery still fails, you can add the device manually using the Manual IP option with the port listed on the compatibility page.

If your intended Primary is an Apple TV: do the initial Restore Home on an iOS, iPadOS, or macOS Controller first — tvOS cannot access iCloud Drive or file pickers and cannot be the restore target. That Controller becomes Primary during the restore. After verifying it works, install on the Apple TV (it joins as a secondary) and switch the Primary designation to it via Settings > Homes > Primary Controller (step 15 below).

1. Back up your configuration — ensure you have a file named RoomieBackup.zip. SimpleControlBackup.zip or older Roomie.plist backups also work.
2. Clear iCloud data — in iOS Settings > [Your Name] > iCloud > Manage Account Storage, delete any items labelled Simple Control or Roomie Remote. Do this on all Controllers you share with. On macOS, use System Settings > Apple ID > iCloud > Manage.
3. Delete all Roomie Remote apps from all Controllers (iOS, tvOS, macOS), including older apps like Intercomm and Simple Control and sister apps like Now Showing.
4. Fully restart (power cycle) all Controllers from step 3.
5. macOS cleanup — for each macOS Controller, delete these folders: ~/Library/Group Containers/group.com.roomie, ~/Library/Containers/maccatalyst.com.roomie.x (and com.roomie.unified), and ~/Library/Containers/Roomie Remote. Some may not exist — that's fine.
6. Verify cleanup — after restarting, repeat step 2 to confirm all iCloud storage entries are gone.
7. Install latest Roomie Remote X on your Primary Controller (logged into the Apple Account that owns your subscription). All Controllers must support iOS/tvOS/macOS 26 or later.
8. Restore your backup via Homes > Restore Home. Select the backup from step 1.
9. Restore Purchases under Settings > About if your subscription doesn't reflect immediately. Subscriptions must be Active and use the same Apple ID for Sign in With Apple.
10. Verify Code Sets — check the downloaded count in Settings shows completion (e.g., 20/20). If still counting, wait. Otherwise press Force Codeset Update and wait for completion.
11. Test Activities on this Primary Controller. Verify it's designated as Primary in the Homes panel and keep it running for all steps below.
12. Additional Controllers (same Apple Account) — install latest Roomie Remote X, launch, wait for the prompt to join the home, allow sync, and verify code sets are complete.
13. Different Apple Account Controllers — first share your HomeKit Home via Apple's Home app from the owning account. Then launch Roomie on the sharee Controller, accept the Instant Home Sharing prompt, and allow it to join. Instant Home Sharing must be enabled in Managed Device Options on Primary Controller.
14. Activate the Home if necessary from the Homes panel (usually automatic).
15. If your intended Primary is an Apple TV — once the Apple TV has joined the home and synchronized, switch the Primary designation to it via Settings > Homes > Primary Controller on any Controller. Verify the Apple TV is elected before taking offline the Controller you used for the restore.